home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 20
/
Cream of the Crop 20 (Terry Blount) (1996).iso
/
bbs
/
ot_263.zip
/
WHATSNEW.263
< prev
Wrap
Text File
|
1996-06-30
|
14KB
|
305 lines
The following is a description of changes in O/T version 2.63 compared
to 2.62a
--------------------------------------------------------------------------
$ = changes
- = bug fixes
+ = new or enhanced feature
! Please note that my ADDRESS has changed!! See the file REGISTER.GER
or REGISTER.ALL for details.
+ added parameter /NOWARN to MOVEBYTEXT command. This will suspend the
warning message to the sysop, if O/T moves a message triggered by this
command.
+ the parameter /TextLine="text" is now valid for ALL commands in
READR.OT and not just for Move-/BounceByText! So the following IS a
valid filter:
Attr /Attr=DH /Adr=* /Textline="15% Mwst" /All
FromAdr /Adr=2:241/1092 /Newadr=2:241/1090 /Textline="not from ISDN"
+ ATTR command: not only /IfOrig but also /IfNOrig does imply /ALL now!
- after checking the readdress file, OTSETUP reported an invalid value
for the amount of command lines if there were more than 255 lines
inside READR.OT. Fixed.
- if a message would have been bounced due to a "bouncebytext" command
in READR.OT *BUT* has been disqualified for bouncing by attribute
definition, O/T did move it erroneously to the suspect path. Fixed.
+ added UTC alternate setting (daylight saving)! See the new UTC submenu
(Global/Switches/UTC) for further details ...
+ Reminder: the old setting "5th <dayname>" has been changed to "last
<dayname>" now! O/T will check internally whether e.g. a 5th Monday
does exist - and if this is not the case it will trigger the reminder
on the 4th Monday!
+ Reminder: added template token %REMDATE%. This will expand to the
reminder date WITHOUT the "added or subtracted" days! Example: you
have defined "every 2. Wednesday --> 3 day(s) before". The second
Wednesday is April, 10th. The reminder will be executed on SUNDAY,
April, 7th! %REMDATE% will exapnd to 10.04.1996 (or - in countries
using the US-format - to 04/10/1996).
$ the ascii file containing the names of EXECUTABLES (to be renamed)
does also apply now to the RenEXE command (previous versions: did
only apply to DenyEXE) [menu: tracker/check attach]
$ if a message is excluded from bouncing (due to attribute definition)
*and* has been readdressed *and* /notify was in effect, O/T did not
generate the netmail notification to the sender of the original
message. This has been changed so that O/T will always write this
notification.
$ changed the product-code field in the packet header to reflect the
statements in FSC-0090 from december 1995.
- fixed a problem with 'remote' messages: if the remote message did
NOT contain a trailing NULL (\0) *AND* the user did only enter the
necessary three lines of information (name, address, subject), O/T did
place this technical information as messagetext in the newly generated
message again. Okok, this could only happen in VERY special
environments under VERY special circumstances .. but it did happen!
Thanks to Roland E. Lipovits for reporting this.
+ the global KILL/SENT switch for generated messages can have to
different exceptions now. (bounce/notify messages)
$ the global KILL/SENT switch does NOT apply to reminder messages
anymore. Each reminder messagee that should be removed after it has
been sent must get the K/S flag in the reminder menu.
+ added value to OTOPT: SET OTOPT=LOGPID will write the PID for every
scanned netmail message to O/T's logfile. This is intended e.g. to
make it a bit more easy to discover hacked versions of certain message
reader products. (Simply search for φ (\237, EDh) in your logfile...)
+ carbon copies: it is possible now to CC *all* messages passing
through your system and not only those addressed to you. To toggle
this behavior, press SPACE on the corresponding CC entry. NOTE: DO
NOT ABUSE THIS FEATURE!! OTSETUP will NOT allow you to use this
feature if either the ZONE or the NET of the sender-address is
wildcarded!
+ in conjunction with the previous described feature it has been
necessary to enhance the message check. O/T will insert a hidden line
(kludge) "^aOT_CC: <main-address>" in every generated carbon copy.
(Note: the MAIN address will be used, not the matching AKA!)
+ O/T will *not* readdress an own carbon copy message to either your
cosyop or one of the six carbon copy addresses anymore. This way you
can globally readdress messages addressed to your co-sysop (-point)
to one of your (node-) AKAs *and* let O/T use the CC:-feature
simultaneously. Confused? Me too .. :-)
Explanation: you want O/T to readdress all incoming netmail messages
to your sysop-point .1 to your main AKA *and* you want it to generate
a carbon copy to your sysop-point .1 as well! This is possible now
because O/T will NOT readdress the generated CC to your .1 back to .0!
$ *NOTE* **IMPORTANT**:
renamed /IFCRASH to /IFDIRECT and /IFNCRASH to /IFNDIRECT (READR.OT)!
The old names are still supported for *this* version! But this WILL
change in the future, so please use the new ones ...
+ added %@IFDIRECT template - block - command! The following statements
are only inserted if the original message was direct/crash/immediate.
%@ifdirect
bla
bla
%@else
blub
%@end
+ added OTOPT=CCB (or CCBOUNCED).
By default O/T will not generate carbon copies to the cosysop anymore
if the original message has been bounced previously. By setting
OTOPT=CCB you can instruct O/T to still generate these carbon copies.
That ONLY applies to CCs to the COSYSOP! Other CCs will only be
generated on non-bounced messages anyway!
+ added switch "Remove path" (Tracker/Switches).
If set to yes, O/T will remove any path information from the subject
if the message is from your own AKA and does not contain the file
attach flag. This way you can easily reply to a file attach message
(your editor will "quote" the original subject with the path
information pointing to an existing path on your system!) without
posting your local HD path structure to the entire world ... ;-)
The same is true for RRQ response messages generated by your O/T and
for all copies to the co-sysop. If the _original_ message did contain
the file attach flag, O/T will remove any existing path information
from the subject line of the newly generated response message.
$ locally generated messages will be included in the carbon copy list to
the cosysop. Previous versions of O/T skipped these messages while
checking for the necessity of CCs. From now on your cosysop will
receive for example your 'Fastecho autocreate' messages as well.
+ added parameter /HOLDNOTIFY{=template.ext{,o|d|b}} to the ATTR command
in READR.OT. If (and only IF) the original message was placed on HOLD
by O/T (using the parameter /Attr=H), the receiver *AND* (!!!!) the
sender will be informed about this fact either using the
'template.ext' or a hardcoded text if only /Holdnotify had been used.
Example:
ATTR /attr=H /ifattach /Adr=* /ifnorig=# /ifndest=#.*
/Holdnotify=otfahold.tem
(to be written in ONE line, of course) will place all file attach
messages not destined to us or one of our points and not originated by
our own system on HOLD and inform the intended receiver about this
using the template \\OT-TEXTFILES-DIR\OTFAHOLD.language-extension !
You may add ",OrigOnly" (komma - O), or ",Destonly" to the template
file name to instruct O/T to only send the notification to either the
originator or t